policy-catalogue: add Asahi Linux entry - #29
Merged
Merged
Conversation
Closes #18. Verbatim excerpts verified against the pinned source before submission.
ecogetaway
pushed a commit
that referenced
this pull request
Jul 31, 2026
…ntries (#30) The single follow-up promised once #21, #23-#29 were in. Count 13 to 20, seven rows added, and the closing line from twelve adopted policies to nineteen plus the one proposal. Each row's distinctive feature is the axis that entry adds to the catalogue rather than a summary of the policy, matching the existing rows: - Home Assistant — the only policy disclosing the project's own AI use, and template bypass as the observable proxy for autonomy - Mesa — the only graduated disclosure vocabulary, and incompatible with both Fedora and Kubernetes on the same mechanism - OpenStreetMap — the only permissive policy asking for no disclosure at all, enforcing on absence of understanding - FreeBSD — the only policy protecting the project as training data; its AI clause is a routing rule rather than a stance - Bevy — the only policy reasoning about its own enforceability - Zig — the strictest, and the only one reaching upstream of the artifact - Asahi Linux — the only stance derived from a pre-existing rule rather than written fresh Every link in the table resolves to a file, and every file in policy-catalogue/ except README and TEMPLATE appears in the table.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
policy-catalogue/asahi-linux.md, closing #18. The policy file isdocs/project/policies/slop.md("Generative AI Policy"), added 2025-07-19, pinned to09810cd.The most distinctive framing in the catalogue — it refuses the industry's vocabulary as part of the policy, naming LLMs "Slop Generators" throughout and arguing that the agent/assistant framing is "a very deliberate attempt to manufacture consent." Worth preserving in a catalogue whose job is mapping policies into one comparable shape: some projects reject the shared vocabulary that mapping depends on.
Three schema signals. The ban is derived from an existing provenance rule rather than written fresh — Asahi already forbade leaked Apple documentation, and extends that to model output on the grounds a model may regurgitate confidential material, with risk scaling by how esoteric the problem space is; changing the AI policy would mean changing the leaked-material policy. Enforcement is numerically specified — exactly one warning, then a permanent ban across all associated spaces — which
repeat_policy: maintainer-discretioncannot express. And environmental cost is a stated rationale, the first in the catalogue and not reducible to copyright, quality or ethics: a tool that resolved every copyright objection still wouldn't satisfy it.AI disclosure (required — we dogfood our own standard)
Attestations (required)
Type of contribution
policy-catalogue/)I've left
policy-catalogue/README.mduntouched across this batch — #21 already edits that table and several PRs touching the same rows would conflict. Happy to send one follow-up PR updating the count and all rows once merge order is settled.Maintainership disclosure: I maintain MergeWarden, a checker in the layer-3 space discussed in #20/#22. This entry documents the project's policy only and makes no claim about any tool.